Apparatuses, computer-implemented methods, and computer program products for generating a collaborative contextual summary interface in association with an audio-video conferencing interface service

ABSTRACT

Various embodiments of the present disclosure provide for generation of a collaborative contextual summary interface in association with an audio-video conferencing interface service. An example embodiment is configured to monitor an active audio-video conference presentation that is configured for display to participating client devices by the audio-video conferencing interface service, identify a first capture content request associated with the active audio-video conference presentation, generate a first captured content data object based at least in part on the first capture content request, correlate a first captured content interface indicator to the first captured content data object, and generate a collaborative contextual summary interface based at least in part on the first captured content data object, wherein the collaborative contextual summary interface comprises the first captured content interface indicator.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/487,387, filed Sep. 28, 2021, which is incorporated by referenceherein in its entirety.

BACKGROUND

Applicant has identified a number of deficiencies and problemsassociated with efficiently identifying and effectively disseminatingpertinent information (e.g., decisions, action items, moments, etc.)among a plurality of users in existing systems that provide multi-partyvirtual meeting environments (e.g., audio/video conferencing). Throughapplied effort, ingenuity, and innovation, many of these identifieddeficiencies and problems have been solved by developing solutions thatare structured in accordance with the embodiments of the presentdisclosure, many examples of which are described in detail herein.

BRIEF SUMMARY

In general, embodiments of the present disclosure provided hereininclude improved apparatuses, methods, systems, and computer programproducts configured for generating and maintaining a collaborativecontextual summary interface in association with an active audio-videoconference presentation provided by an audio-video conferencinginterface service. In accordance with one exemplary embodiment of thepresent disclosure, an apparatus is configured to generate acollaborative contextual summary interface in association with anaudio-video conferencing interface service, the apparatus comprising atleast one processor and at least one memory, the at least one memoryhaving computer-coded instructions therein, wherein the computer-codedinstructions are configured to, in execution with the at least oneprocessor, cause the apparatus to monitor an active audio-videoconference presentation that is configured for display to participatingclient devices by the audio-video conferencing interface service,wherein the active audio-video conference presentation is assigned apresentation identifier; identify a first capture content requestassociated with the active audio-video conference presentation, whereinthe first capture content request comprises a first user identifierassociated with one of the participating client devices, a first capturetype identifier, and an initial timestamp value associated with firstcapture content request; generate a first captured content data objectbased at least in part on the first capture content request, wherein thefirst captured content data object is assigned a first captured contentidentifier; correlate a first captured content interface indicator tothe first captured content data object, wherein the first capturedcontent interface indicator corresponds to the capture type identifier;and generate a collaborative contextual summary interface based at leastin part on the first captured content data object, wherein thecollaborative contextual summary interface comprises the first capturedcontent interface indicator, and wherein the collaborative contextualsummary interface is configured for rendering to at least the one of theparticipating client devices associated with the first user identifier.

In some embodiments, the active audio-video conference presentation is alive streaming presentation displayed in real time by the audio-videoconferencing interface service to each of the participating clientdevices. In still further embodiments, the active audio-video conferencepresentation is a stored playback presentation displayed to at least theone of the participating devices associated with the first useridentifier.

In some embodiments, the first captured content interface indicator isselected from a plurality of captured content interface indicators, eachcaptured content interface indicator associated with a different capturetype identifier. In certain embodiments, the capture type identifier isselected from one of capture note type identifier, assign action typeidentifier, capture decision type identifier, record moment typeidentifier, external service push type identifier, capture screenshottype identifier, object state change type identifier, capture questiontype identifier, capture answer type identifier, capture object linktype identifier, or capture sprint start type identifier.

In some embodiments, the collaborative contextual summary interfacecomprises a visual playback representation element, the visual playbackrepresentation element representing a time duration of the activeaudio-video conference presentation. In still further embodiments, thecomputer-coded instructions are further configured to, in execution withthe at least one processor, cause the apparatus to determine a positionof the first captured content interface indicator relative to the visualplayback representation element, wherein the determined position isbased at least in part on the initial timestamp value relative to thetime duration of active-video conference presentation; and causerendering of the collaborative contextual summary interface to at leastthe one of the participating client devices associated with the firstuser identifier, wherein the first captured content interface indicatoris displayed to the collaborative contextual summary interface in thedetermined position relative to the visual playback representationelement. In still further embodiments, upon detection of user engagementwith the first captured content interface indicator, the computer-codedinstructions are further configured to, in execution with the at leastone processor, cause the apparatus to update the collaborativecontextual summary interface to display a stored playback presentationof at least a portion of the active audio-video conference presentation,wherein the stored playback presentation commences with rendering ofmedia content of the active audio-video conference presentationcorresponding to the initial timestamp value associated with the firstcaptured content interface indicator.

In some embodiments, the collaborative contextual summary interfacefurther comprises a transcription interface, the transcription interfacecomprising textual transcription data substantially synchronized withthe active audio-video conference presentation. In still furtherembodiments, the transcription interface comprises one or moreannotation bubble objects associated with the textual transcription dataand wherein one of the one or more annotation bubble objects comprisesthe first captured content interface indicator. In certain embodiments,upon detection of user engagement with the first captured contentinterface indicator, the computer-coded instructions are furtherconfigured to, in execution with the at least one processor, cause theapparatus to update the collaborative contextual summary interface todisplay a stored playback presentation of at least a portion of theactive audio-video conference presentation, wherein the stored playbackpresentation commences with rendering of media content of the activeaudio-video conference presentation corresponding to the initialtimestamp value associated with the first captured content interfaceindicator. In still further embodiments, the first capture contentrequest further comprises a concluding timestamp value and the storedplayback presentation concludes with rendering of media content of theactive audio-video conference presentation corresponding to theconcluding timestamp value. In certain embodiments, the capture typeidentifier is a record moment type identifier.

In some embodiments, the computer-coded instructions are furtherconfigured to, in execution with the at least one processor, cause theapparatus to store the collaborative contextual summary interface in acollaboration repository in association with the presentationidentifier. In certain embodiments, the collaborative contextual summaryinterface further comprises a share summary interface element. Infurther embodiments, upon detection of user engagement with the sharesummary interface element, the computer-coded instructions areconfigured to, in execution with the at least one processor, cause theapparatus to generate a collaborative contextual summary interfaceobject that is configured to cause a client device to render thecollaborative contextual summary interface. In still furtherembodiments, the computer-coded instructions are configured to, inexecution with the at least one processor, cause the apparatus to outputthe collaborative contextual summary interface object to at least one ofthe participating client devices, wherein the at least one of theparticipating client devices is not associated with the first useridentifier; and upon detection of user engagement with the collaborativecontextual summary interface object, cause rendering of thecollaborative contextual summary interface to the at least one of theparticipating client devices. In other embodiments, the computer-codedinstructions are configured to, in execution with the at least oneprocessor, cause the apparatus to output the collaborative contextualsummary interface object to at least one non-participating clientdevice; and upon detection of user engagement with the collaborativecontextual summary interface object, cause rendering of thecollaborative contextual summary interface to the at least onenon-participating client device.

In some embodiments, the computer-coded instructions are furtherconfigured to, in execution with the at least one processor, cause theapparatus to identify a second capture content request associated withthe active audio-video conference presentation, wherein the secondcapture content request comprises the first user identifier, a secondcapture type identifier, the presentation identifier, and an initialtimestamp value associated with second capture content request; generatea second captured content data object based at least in part on thesecond capture content request, wherein the second captured content dataobject is assigned a second captured content identifier; correlate asecond captured content interface indicator to the second capturedcontent data object, wherein the second captured content interfaceindicator corresponds to the second capture type identifier; and updatethe collaborative contextual summary interface based at least in part onthe second captured content data object, wherein the collaborativecontextual summary interface comprises the first captured contentinterface indicator and the second captured content interface indicator.

In some embodiments, the computer-coded instructions are furtherconfigured to, in execution with the at least one processor, cause theapparatus to identify a second capture content request associated withthe active audio-video conference presentation, wherein the secondcapture content request comprises a second user identifier associatedwith one of the participating client devices, a second capture typeidentifier, and an initial timestamp value associated with secondcapture content request; generate a second captured content data objectbased at least in part on the second capture content request, whereinthe second captured content data object is assigned a second capturedcontent identifier; correlate a second captured content interfaceindicator to the second captured content data object, wherein the secondcaptured content interface indicator corresponds to the second capturetype identifier; and update the collaborative contextual summaryinterface based at least in part on the second captured content dataobject, wherein the collaborative contextual summary interface comprisesthe first captured content interface indicator and the second capturedcontent interface indicator, and wherein the collaborative contextualsummary interface is configured for rendering to at least the one of theparticipating client devices associated with the first user identifierand at least the one of the participating client devices associated withthe second user identifier. In some further embodiments, the activeaudio-video conference presentation is a live streaming presentationdisplayed in real time by the audio-video conferencing interface serviceto each of the participating client devices, and wherein updating thecollaborative contextual summary interface based at least in part on thesecond captured content data object comprises updating the collaborativecontextual summary interface in real time. In still other embodiments,the active audio-video conference presentation is a stored playbackpresentation, and wherein updating the collaborative contextual summaryinterface based at least in part on the second captured content dataobject comprises updating the collaborative contextual summary interfacein real time.

The above summary is provided merely for purposes of summarizing someexample embodiments to provide a basic understanding of some aspects ofthe present disclosure. Accordingly, it will be appreciated that theabove-described embodiments are merely examples and should not beconstrued to narrow the scope or spirit of the present disclosure in anyway. It will be appreciated that the scope of the present disclosureencompasses many potential embodiments in addition to those heresummarized, some of which will be further described below. Otherfeatures, aspects, and advantages of the subject matter will becomeapparent from the description, the drawings, and the claims.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Having thus described certain example embodiments of the presentdisclosure in general terms above, non-limiting and non-exhaustiveembodiments of the subject disclosure will now be described withreference to the accompanying drawings which are not necessarily drawnto scale. The components illustrated in the accompanying drawings may ormay not be present in certain embodiments described herein. Someembodiments may include fewer (or more) components than those shown inthe drawings:

FIG. 1 illustrates an example collaborative contextual summary interfacemanagement system configured to communicate with an audio-videoconferencing interface service and two or more client devices inaccordance with some example embodiments described herein;

FIG. 2 is a schematic block diagram of example circuitry for use in acollaborative contextual summary interface server in accordance withsome example embodiments described herein;

FIG. 3 is a schematic block diagram of example circuitry for use in aclient device in accordance with some example embodiments describedherein;

FIG. 4 illustrates an example collaborative contextual summary interfacestructured in accordance with some example embodiments described herein;

FIG. 5A is a flowchart illustrating example operations for generating acollaborative contextual summary interface in accordance with variousaspects and embodiments of the subject disclosure;

FIG. 5B is a signal diagram of an example data flow in accordance withvarious aspects and embodiments of the subject disclosure;

FIG. 6 is a flowchart illustrating example operations for updating acollaborative contextual summary interface in accordance with variousaspects and embodiments of the subject disclosure; and

FIG. 7 is a flowchart illustrating example operations for updating acollaborative contextual summary interface in accordance with variousaspects and embodiments of the subject disclosure

DETAILED DESCRIPTION

One or more embodiments now will be more fully described with referenceto the accompanying drawings, wherein like reference numerals are usedto refer to like elements throughout. In the following description, forpurposes of explanation, numerous specific details are set forth inorder to provide a thorough understanding of the various embodiments. Itis evident, however, that the various embodiments can be practicedwithout these specific details (and without applying to any particularnetworked environment or standard). It should be understood that some,but not all embodiments are shown and described herein. Indeed, theembodiments may be embodied in many different forms, and accordinglythis disclosure should not be construed as limited to the embodimentsset forth herein. Rather, these embodiments are provided so that thisdisclosure will satisfy applicable legal requirements. As used herein,the description may refer to an example “apparatus.” However, elementsof the apparatus described herein may be equally applicable to theclaimed system, method, and computer program product. Accordingly, useof any such terms should not be taken to limit the spirit and scope ofembodiments of the present disclosure.

Overview

Individuals and organizations routinely use audio-video conferencingservices (e.g., Zoom®, GoToMeeting®, BlueJeans®, Webex®, Teams®, GoogleMeet®, or the like) to allow geographically-dispersed users to remotelycommunicate and collaborate within and across organizations usingindividual computing devices (e.g., laptops, desktops, smart phones,servers, and/or the like). A variety of information such as importantdecisions, action items, meeting moments, and/or the like may occurduring such virtual meetings and participants may desire to capture,point to, highlight, or otherwise emphasize such moments of the virtualmeeting to, for example, revisit later or to share with other teammembers.

The volume of pertinent information created during virtual meetings hascontinued to increase exponentially as more and more individuals useaudio-video conferencing services to engage in virtual collaboration. Itis undesirable to require participants to manually organize, circulate,and maintain meeting minutes in an attempt to retain or capture actionitems, meeting moments, insights, decisions, or the like. It is alsoundesirable to require users to review a recording of the meeting in itsentirety or to painstakingly trim down a recording of the meeting to itsrelevant portions in an attempt to preserve context related to suchoutcomes. Accordingly, the inventors have determined it would bedesirable and advantageous to create a collaborative contextual summaryinterface management system that is configured to programmaticallyidentify or suggest, and effectively disseminate, pertinent content,such as key decisions, action items, assignments, important meetingmoments, and other highlights from an audio-video conferencepresentation (e.g., Zoom® meeting) to a plurality of users in acontextually relevant manner.

Various embodiments of the present disclosure provide apparatuses,systems, computer-implemented methods, and computer program products forcapturing content in a virtual meeting and generating, maintaining,and/or sharing a collaborative contextual summary interface to aplurality of users, including those users who participated in the livepresentation of the meeting and/or those users who did not. Some suchembodiments enhance meeting communication methods by reducingmiscommunication, ensuring team alignment, increasing post-meetingaccountability, and otherwise reducing time and cost expendituresincurred in culling and disseminating relevant information from themeeting.

Definitions

As used herein, the term “audio-video conferencing interface service”refers to an application, program, platform, and/or service configuredfor providing virtual video and/or audio conferencing (e.g., activeaudio-video conference presentation), webinars, live chats, streamingservices, screen-sharing, and other real-time collaborative audio and/orvideo capabilities configured for display to a plurality ofparticipating client devices. Non-limiting examples of an audio-videoconferencing interface service include Zoom®, BlueJeans®, Webex®,Teams®, Google Meet®, and the like.

In some embodiments, an audio-video conferencing interface service ishosted by an “external resource” such that it is associated with athird-party controlled system and is configured for authenticatedcommunication with a collaborative contextual summary interfacemanagement system to provide audio-video conferencing functionality toparticipating client devices. An external resource providesfunctionality not provided natively by the collaboration managementsystem. The external resource operates on a compiled code base orrepository that is separate and distinct from that which supports thecollaborative contextual summary interface management system. In someembodiments, the external resource may communicate with thecollaborative contextual summary interface management system, and viceversa, through one or more application program interfaces (APIs). Insome embodiments, an audio-video conferencing interface service ishosted by the collaborative contextual summary interface managementsystem.

The term “collaborative contextual summary interface management system”refers to a software platform and associated hardware that is configuredto support, maintain, and manage collaborative contextual summaryinterface data associated with capturing, bookmarking, highlighting, orotherwise emphasizing selected content in an audio-video conferencinginterface service. In some embodiments, the collaborative contextualsummary interface management system, or a portion thereof, is at leastpartially configured to operate as a portion (e.g., plug-in, add-on,extension, etc.) of an audio-video conferencing interface service. Insome embodiments, the collaborative contextual summary interfacemanagement system, or a portion thereof, is configured to operate oncompiled code bases or repositories that are separate and distinct(e.g., a standalone collaboration server or other computing device) fromthe audio-video conferencing interface service and/or one or more clientdevices associated with one or more users.

The term “collaborative contextual summary interface server” refers to asoftware platform and associated hardware that is configured to generateand/or manage collaborative contextual summary interface(s) inassociation with an audio-video conferencing interface service. Thecollaborative contextual summary interface server is accessible via oneor more computing devices, is configured to monitor active audio-videoconference presentation(s), identify and/or receive capture contentrequests, generate a collaborative contextual summary interface, andaccess one or more data repositories, such as a collaborationrepository. The functionality of the collaborative contextual summaryinterface server may be provided via a single server or a collection ofservers having a common functionality, or the functionality of thecollaborative contextual summary interface server may be segmented amonga plurality of servers or collections of servers performing subsets ofthe described functionality of the collaborative contextual summaryinterface server, such as in a cloud networking environment.

A collaborative contextual summary interface server may update and/ormaintain a shared dynamic collaborative contextual summary interfacethat provides for team collaborative work. For example, in someembodiments, the collaborative contextual summary interface server isconfigured to enable a plurality of users (e.g., participating and/ornon-participating) to access, display, and/or modify/edit a dynamiccollaborative contextual summary interface at the same time. Changesmade by respective users to a shared dynamic collaborative contextualsummary interface can be automatically stored/saved and synced betweenall users in real-time. For example, a first participating user mayidentify and assign an action associated with a selected portion of alive streaming presentation and other users may be able to view theupdated dynamic collaborative contextual summary interface in real time,as well as capture additional content with respect to the live streamingpresentation.

The term “collaborative contextual summary interface data repository”refers to a location, such as database stored on a memory device, whichis accessible by one or more computing devices for retrieval and storageof data associated with collaborative contextual summary interface(s).For example, the collaborative contextual summary interface datarepository includes one or more of collaborative contextual summaryinterface(s), presentation identifier(s), user identifier(s), capturetype identifier(s), captured content identifier(s), and/or the like. Thecollaborative contextual summary interface data repository may be adedicated device and/or a part of a larger repository. The collaborativecontextual summary interface data repository may be dynamically updatedor be static. In some embodiments, the collaborative contextual summaryinterface data repository is encrypted in order to limit unauthorizedaccess of such collaborative contextual summary interface data.

The terms “client device”, “computing device”, “user device”, and thelike may be used interchangeably to refer to computer hardware that isconfigured (either physically or by the execution of software) to accessone or more of an application, service, or repository made available bya server (e.g., apparatus of the present disclosure) and, among variousother functions, is configured to directly, or indirectly, transmit andreceive data. The server is often (but not always) on another computersystem, in which case the client device accesses the service by way of anetwork. Example client devices include, without limitation, smartphones, tablet computers, laptop computers, wearable devices (e.g.,integrated within watches or smartwatches, eyewear, helmets, hats,clothing, earpieces with wireless connectivity, and the like), personalcomputers, desktop computers, enterprise computers, the like, and anyother computing devices known to one skilled in the art in light of thepresent disclosure. In some embodiments, a client device is associatedwith a user. In some embodiments, an association is created by a clientdevice transmitting authentication information associated with the userfor the selected active audio-video conference presentation to theaudio-video conferencing interface service and/or a collaborativecontextual summary interface management system.

A “participating client device” of an active audio-video conferencepresentation refers to a client device associated with a user identifieridentified as disposed, or having been disposed, in a real-timecommunicative relation with the live stream presentation of the activeaudio-video conference presentation. The term “non-participating clientdevice” refers to a client device that may be configured for access toan active audio-video conference presentation, but which is notassociated with a user identifier identified as disposed, or having beendisposed, in a real-time communicative relation with the live streampresentation of the selected active audio-video conference presentation.

The term “capture content request” refers to an electrically generateddigital object created by a computing device (e.g., participating clientdevice) indicating that a user has provided an input comprising arequest to capture content for highlighting, tagging, bookmarking,illustrating, and/or otherwise emphasizing some portion of the activeaudio-video presentation. In certain embodiments of the presentdisclosure, the selected content of the capture content request can beshared among and accessed by participating client devices and, in someinstances, non-participating client devices, on a collaborativecontextual summary interface.

A capture content request may be represented via a temporary code thatis transmitted to a recipient (e.g., a collaborative contextual summaryinterface server) as an indication that a user has made the request. Toprovide further context, in one embodiment, a capture content request isgenerated in response to a user interaction or user engagement with acomputing device (e.g., a participating client device ornon-participating client device) wherein a user causes the computingdevice to generate a capture content request by interacting with, forexample, a specific capture type actuator button or interface elementrendered on a visual display of the computing device (e.g., a userclicking on a “Record a Moment” icon during an active audio-videoconference presentation) indicating an intention to capture content. Insome embodiments, the capture content request is associated with avariety of metadata such as one or more of a initiating user identifier,a presentation identifier, a capture type identifier, an initialtimestamp value (e.g., associated with the selected portion of theactive audio-video conference presentation), a concluding timestampvalue, and/or other data for use in generating, updating, or otherwisesupporting a collaborative contextual summary interface as describedherein. The capture content request is configured to trigger theapparatus (e.g., a collaborative contextual summary interface server) toinitiate a capture content process that may culminate in generation orupdating of a collaborative contextual summary interface.

The term “collaborative contextual summary interface” refers to a userinterface or sub-user interface comprising one or more captured contentinterface indicator(s) that is rendered to a visual display and isspecially configured to enable a user to access, review, create,modify/edit, and/or identify captured content associated with anaudio-video conference presentation that was monitored by acollaborative contextual summary interface management system (e.g.,collaborative contextual summary interface server) during an activepresentation of the audio-video conference presentation. In someembodiments, a collaborative contextual summary interface optionallycomprises one or more of a visual playback representation element, aplayback interface, a transcription interface comprising textualtranscription data, one or more annotation bubble objects, a sharesummary interface element, and an export captured content interfaceelement. Exemplary collaborative contextual summary interfaces may berendered in any desired form including, but not limited to, as a mobileapplication for display on a mobile computing device (e.g., asmartphone, table computer, etc.), a webpage or website for display on amobile or non-mobile computing device via the Internet, and the like.For example, the collaborative contextual summary interface 400 of FIG.4 is an example of a collaborative contextual summary interface.

The term “captured content interface indicator” refers to a renderableindicator displayed to a collaborative contextual summary interface, thecaptured content interface indicator associated with the capturedcontent identified by a capture content request. In some embodiments, acaptured content interface indicator is selected from a plurality ofcaptured content interface indicators, each captured content interfaceindicator associated with a different capture type (e.g., capture typeidentifier). That is, in some embodiments, captured content interfaceindicators are visually different based at least in part on selectedcapture type associated with the corresponding capture content request.In some embodiments, the captured content interface indicator isrendered to a position or location of the collaborative contextualsummary interface such that it is indicative of the initial timestampvalue relative to a visual playback representation element. For example,the captured content interface indicators 410 of FIG. 4 are examples ofcaptured content interface indicators.

The term “captured content data object” refers to one or moreelectronically managed data representing the captured content associatedwith and/or identified by a captured content request. The capturedcontent data object is a data representation of the captured contentthat is created by a computing device (e.g., collaborative contextualsummary interface server) in response to identifying and/or receiving acaptured content request. The captured content data object is correlatedwith a captured content interface indicator that is configured to bedisplayed to a collaborative contextual summary interface such thatsubsequent user engagement with or user selection of the capturedcontent interface indicator initiates a process to view the correlatedcaptured content represented by the captured content data object. In anon-limiting example context, a captured content data object refers toelectronically managed data that represents the pertinent content of theactive audio-video conference that was bookmarked by a user, such as akey decision or approval to develop a software product, an action item,a task assignment to fix a specified bug, or other important meetingmoment that should be highlighted or pushed to one or more relevantusers to get the work done. A captured content data object is assigned acaptured content identifier by a computing device (e.g., collaborativecontextual summary interface server) and can be stored in a datarepository (e.g., collaborative contextual summary interface datarepository) as the data representation of the corresponding capturedcontent that was highlighted, tagged, bookmarked, illustrated, and/orotherwise emphasized in association with a capture content request.

As used herein, the term “presentation identifier” refers to one or moreitems of data by which an audio-video conference presentation may beidentified within a collaborative contextual summary interfacemanagement system. For example, a presentation identifier may comprisetext string(s), numerical character(s), alphabetical character(s),alphanumeric code(s), ASCII character(s), a pointer, an IP address, aMAC address, a memory address, other unique identifier, or a combinationthereof.

The term “timestamp value” refers to a sequence of characters or encodedinformation identifying when a certain event occurs. In someembodiments, one or more timestamp values are captured, converted to,and/or stored in a primary time standard. For example, in someembodiments, one or more timestamp values are captured, converted to,and/or stored according to a Coordinated Universal Time (UTC) globalstandard. In some embodiments, one or more timestamp values are arelative timestamp value such that they identify when a certain eventoccurs in relation to another event or time (e.g., elapsed time relativeto the start of a selected active audio-video conference presentation).In certain embodiments, such relative timestamp values are converted toand stored in the UTC global standard, thereby allowing calculations andcomparisons to be performed regardless of source. For example, in someembodiments, timestamp values associated with the capture contentrequest are substantially synchronized with the active audio-videoconference presentation and/or the textual transcription data.

An “initial timestamp value” associated with a capture content requestrefers to a timestamp value identifying when the capture of mediacontent begins. For example, in some embodiments, the capture of mediacontent begins with a keystroke associated with a capture note type oruser interaction with an indicator or icon associated with record momenttype to record a moment. In some embodiments, a capture content requestis associated with a selected capture type (e.g., record a moment) suchthat a “concluding timestamp value” is further identified. A “concludingtimestamp value” refers to a timestamp value identifying when thecapture of media content ends such that all interactions (e.g.,keystrokes, video, etc.) are captured in the time interval between theinitial timestamp value and the concluding timestamp value.

As used herein, the term “capture type” refers to a data parameter,attribute, or the like that defines the type of capture to be performedas associated with a captured content request. The collaborativecontextual summary interface management system supports one or morecapture types with respect to the selected active audio-video conferencepresentation. For example, a capture type (e.g., capture note typeidentifier, assign action type identifier, capture decision typeidentifier, record moment type identifier, external service push typeidentifier, capture screenshot type identifier, object state change typeidentifier, capture question type identifier, capture answer typeidentifier, capture object link type identifier, sprint start capturetype identifier, and the like) for a corresponding capture contentrequest may identify the corresponding capture content request as arequest to record a moment, capture a note, assign an action, capture adecision, push content to an external service, capture a question,capture an answer, capture a screenshot, capture state change in anobject (e.g., Jira® ticket being resolved), capture a link or card of anobject being shared during the active audio-video conferencepresentation (e.g., capture link to the Confluence® page being sharedduring the presentation), capture a sprint start (e.g., identify ticketsincluded in a sprint in association with a sprint planning meeting),and/or the like.

In certain embodiments, a user may be permitted to identify a capturetype to be associated with a captured content request via userengagement with a client device to select a capture type from arenderable menu listing the available capture types, the menu renderedto a visual display of the client device. In some embodiments, thecollaborative contextual summary interface server is configured toprogrammatically detect and/or determine a meeting type such that one ormore different available capture types are displayed, For example, in anon-limiting example, a collaborative contextual summary interfaceserver determines that the meeting type is a sprint planning meetingsuch that renderable menu listing further includes a capture sprintstart capture type as an available capture type.

As used herein, the term “capture type identifier” refers to one or moreitems of data by which a capture type may be identified within acollaborative contextual summary interface management system. Forexample, a capture type identifier may comprise text string(s),numerical character(s), alphabetical character(s), alphanumeric code(s),ASCII character(s), a pointer, an IP address, a MAC address, a memoryaddress, other unique identifier, or a combination thereof.

The term “visual playback representation element” refers to a renderablecomponent configured to visually depict a time duration of an activeaudio-video conference presentation. A non-limiting example of a visualplayback representation element is a video timeline or scroll bar. Incertain embodiments, one or more captured content interface indicatorsare rendered to the visual playback representation element. For example,the visual playback representation element 420 of FIG. 4 is an exampleof a collaborative contextual summary interface.

The term “textual transcription data” refers to the data outputresulting from one or more transcription operations performed withrespect to one or more audio inputs of an audio visual conferencepresentation. In certain embodiments, as a non-limiting example, textualtranscription data is generated via voice-to-text conversion of an audiocomponent of the active audio-video conference presentation, such asautomatic speech recognition (ASR). In a non-limiting example,transcription of the audio component of the active audio-videoconference presentation is automatically executed in real-time so as tobe substantially synchronized with a video component of the activeaudio-video conference presentation. In some embodiments, the textualtranscription data is generated by and received from the audio-videoconferencing interface service in association with the monitored activeaudio-video conferencing interface service. In some embodiments, thetextual transcription data is generated by the collaborative contextualsummary interface server in association with the monitored activeaudio-video conferencing interface service. In some embodiments, thetextual transcription data is generated during a live streamingpresentation (e.g., in real time) of an active audio-video conferencepresentation. In still further embodiments, the textual transcriptiondata is generated from a stored playback presentation of an activeaudio-video conference presentation.

The term “transcription interface” refers to a user interface component,sub-user interface component, or modal that is rendered to acollaborative contextual summary interface and is specially configuredto display a textual representation of the textual transcription dataassociated with a corresponding audio-video conference presentation. Insome embodiments, a transcription interface is configured to enable auser to create, identify, review, and/or modify/edit captured contentassociated with a corresponding audio-video conference presentation.Exemplary transcription interfaces may be rendered in any desired form.For example, the transcription interface 440 of FIG. 4 is an example ofa transcription interface.

The term “collaborative contextual summary interface object” refers to adata structure that includes data representing a collaborativecontextual summary interface. For instance, the collaborative contextualsummary interface object can be provided to a client device and acollaborative contextual summary interface can be configured based onthe collaborative contextual summary interface object. The collaborativecontextual summary interface object is a data structure representing thecollaborative contextual summary interface that is created and/ormodified by a computing device (e.g., collaborative contextual summaryinterface server) in response to identifying and/or receiving one ormore captured content request(s). A collaborative contextual summaryinterface object can be stored in a data repository (e.g., collaborativecontextual summary interface data repository) as the data representationof the corresponding collaborative contextual summary interface.

The terms “data,” “content,” “digital content,” “digital contentobject,” “signal”, “information,” and similar terms may be usedinterchangeably to refer to data capable of being transmitted, received,and/or stored in accordance with embodiments of the present invention.Thus, use of any such terms should not be taken to limit the spirit andscope of embodiments of the present invention. Further, where acomputing device is described herein to receive data from anothercomputing device, it will be appreciated that the data may be receiveddirectly from another computing device or may be received indirectly viaone or more intermediary computing devices, such as, for example, one ormore servers, relays, routers, network access points, base stations,hosts, and/or the like, sometimes referred to herein as a “network.”Similarly, where a computing device is described herein to send data toanother computing device, it will be appreciated that the data may betransmitted directly to another computing device or may be transmittedindirectly via one or more intermediary computing devices, such as, forexample, one or more servers, relays, routers, network access points,base stations, hosts, and/or the like.

The terms “computer-readable storage medium” refers to a non-transitory,physical or tangible storage medium (e.g., volatile or non-volatilememory), which may be differentiated from a “computer-readabletransmission medium,” which refers to an electromagnetic signal. Such amedium can take many forms, including, but not limited to anon-transitory computer-readable storage medium (e.g., non-volatilemedia, volatile media), and transmission media. Transmission mediainclude, for example, coaxial cables, copper wire, fiber optic cables,and carrier waves that travel through space without wires or cables,such as acoustic waves and electromagnetic waves, including radio,optical, infrared waves, or the like. Signals include man-made, ornaturally occurring, transient variations in amplitude, frequency,phase, polarization or other physical properties transmitted through thetransmission media.

Examples of non-transitory computer-readable media include a magneticcomputer readable medium (e.g., a floppy disk, hard disk, magnetic tape,any other magnetic medium), an optical computer readable medium (e.g., acompact disc read only memory (CD-ROM), a digital versatile disc (DVD),a Blu-Ray disc, or the like), a random access memory (RAM), aprogrammable read only memory (PROM), an erasable programmable read onlymemory (EPROM), a FLASH-EPROM, or any other non-transitory medium fromwhich a computer can read. The term computer-readable storage medium isused herein to refer to any computer-readable medium except transmissionmedia. However, it will be appreciated that where embodiments aredescribed to use a computer-readable storage medium, other types ofcomputer-readable mediums can be substituted for or used in addition tothe computer-readable storage medium in alternative embodiments.

As used herein, the term “user identifier” refers to one or more itemsof data by which a user may be identified within a collaborationmanagement system. For example, a user identifier may comprise textstring(s), numerical character(s), alphabetical character(s),alphanumeric code(s), ASCII character(s), a pointer, an IP address, aMAC address, a memory address, other unique identifier, or a combinationthereof.

The terms “application,” “software application,” “app,” “product,”“service” or similar terms refer to a computer program or group ofcomputer programs designed to perform coordinated functions, tasks, oractivities for the benefit of a user or group of users. A softwareapplication can run on a server or group of servers (e.g., a physical orvirtual servers in a cloud-based computing environment). In certainembodiments, an application is designed for use by and interaction withone or more local, networked or remote computing devices, such as, butnot limited to, client devices. Non-limiting examples of an applicationcomprise workflow engines, service desk incident management, teamcollaboration suites, cloud services, word processors, spreadsheets,accounting applications, web browsers, email clients, media players,file viewers, videogames, audio-video conferencing, and photo/videoeditors. In some embodiments, an application is a cloud product.

The term “comprising” means including but not limited to and should beinterpreted in the manner it is typically used in the patent context.Use of broader terms such as comprises, includes, and having should beunderstood to provide support for narrower terms such as consisting of,consisting essentially of, and comprised substantially of.

The phrases “in one embodiment,” “according to one embodiment,” and thelike generally mean that the particular feature, structure, orcharacteristic following the phrase may be included in the at least oneembodiment of the present invention and may be included in more than oneembodiment of the present invention (importantly, such phrases do notnecessarily refer to the same embodiment).

The terms “illustrative,” “example,” “exemplary” and the like are usedherein to mean “serving as an example, instance, or illustration” withno indication of quality level. Any implementation described herein as“exemplary” is not necessarily to be construed as preferred oradvantageous over other implementations.

The terms “about,” “approximately,” or the like, when used with anumber, may mean that specific number, or alternatively, a range inproximity to the specific number, as understood by persons of skill inthe art field.

If the specification states a component or feature “may,” “can,”“could,” “should,” “would,” “preferably,” “possibly,” “typically,”“optionally,” “for example,” “often,” or “might” (or other suchlanguage) be included or have a characteristic, that particularcomponent or feature is not required to be included or to have thecharacteristic. Such component or feature may be optionally included insome embodiments, or it may be excluded.

The term “set” refers to a collection of one or more items.

The term “plurality” refers to two or more items.

The term “or” is used herein in both the alternative and conjunctivesense, unless otherwise indicated.

Having set forth a series of definitions called-upon throughout thisapplication, an example system architecture and example apparatus isdescribed below for implementing example embodiments and features of thepresent disclosure.

Example System Architecture

Methods, apparatuses, systems, and computer program products of thepresent disclosure may be embodied by any of a variety of computingdevices. For example, the method, apparatus, system, and computerprogram product of an example embodiment may be embodied by a networkeddevice, such as a server or other network entity, configured tocommunicate with one or more devices, such as one or more clientdevices. Additionally, or alternatively, the computing device mayinclude fixed computing devices, such as a personal computer or acomputer workstation. Still further, example embodiments may be embodiedby any of a variety of mobile devices, such as a portable digitalassistant (PDA), mobile telephone, smartphone, laptop computer, tabletcomputer, wearable, or any combination of the aforementioned devices.

With reference to FIG. 1 , an example computing system 100 within whichsome embodiments of the present disclosure operate is illustrated. Inparticular, FIG. 1 illustrates an example collaborative contextualsummary interface management system 200 configured to communicate withan audio-video conferencing interface service and/or two or more clientdevices 101A-101N in accordance with some example embodiments describedherein. Users may access a collaborative contextual summary interfacemanagement system 200 via a communications network 102 using one or moreof client devices 101A-101N. Collaborative contextual summary interfacemanagement system 200 may comprise a collaborative contextual summaryinterface server 210 in communication with at least one repository, suchas collaborative contextual summary interface data repository 215. Suchrepository(ies) may be hosted by the collaborative contextual summaryinterface server 210 or otherwise hosted by devices in communicationwith the collaborative contextual summary interface server 210. Thecollaborative contextual summary interface management system 200 is, insome embodiments, able to generate a collaborative contextual summaryinterface in association with an audio-video conferencing interfaceservice, as will be described below.

Collaborative contextual summary interface server 210 may includecircuitry, networked processors, or the like configured to perform someor all of the collaborative contextual summary interface server-basedprocesses described herein (e.g., generate and/or transmit commands andinstructions for rendering a collaborative contextual summary interfaceto client devices 101A-101N, using data from, for example, collaborativecontextual summary interface data repository 215), and may be anysuitable network server and/or other type of processing device. In thisregard, the collaborative contextual summary interface server 210 may beembodied by any of a variety of devices, for example, the collaborativecontextual summary interface server 210 may be embodied as a computer ora plurality of computers. For example, collaborative contextual summaryinterface server 210 may be configured to receive/transmit data and mayinclude any of a variety of fixed terminals, such as a server, desktop,or kiosk, or it may comprise any of a variety of mobile terminals, suchas a portable digital assistant (PDA), mobile telephone, smartphone,laptop computer, tablet computer, or in some embodiments, a peripheraldevice that connects to one or more fixed or mobile terminals. Exampleembodiments contemplated herein may have various form factors anddesigns but will nevertheless include at least the componentsillustrated in FIG. 2 and described in connection therewith. In someembodiments, collaborative contextual summary interface server 210 maybe located remotely from the collaborative contextual summary interfacedata repository 215, although in other embodiments, the collaborativecontextual summary interface server 210 may comprise the collaborativecontextual summary interface data repository 215. The collaborativecontextual summary interface server 210 may, in some embodiments,comprise several servers or computing devices performing interconnectedand/or distributed functions. Despite the many arrangements contemplatedherein, collaborative contextual summary interface server 210 is shownand described herein as a single computing device to avoid unnecessarilyovercomplicating the disclosure.

Collaborative contextual summary interface server 210 can communicatewith one or more client devices 101A-101N and/or an audio-videoconferencing interface service 105 via communications network 102.Communications network 102 may include any one or more wired and/orwireless communication networks including, for example, a wired orwireless local area network (LAN), personal area network (PAN),metropolitan area network (MAN), wide area network (WAN), or the like,as well as any hardware, software and/or firmware required forimplementing the one or more networks (e.g., network routers, switches,hubs, etc.). For example, communications network 102 may include acellular telephone, mobile broadband, long term evolution (LTE),GSM/EDGE, UMTS/HSPA, IEEE 802.11, IEEE 802.16, IEEE 802.20, Wi-Fi,dial-up, and/or WiMAX network. Furthermore, the communications network102 may include a public network, such as the Internet, a privatenetwork, such as an intranet, or combinations thereof, and may utilize avariety of networking protocols now available or later developedincluding, but not limited to TCP/IP based networking protocols. Forinstance, the networking protocol may be customized to suit the needs ofthe collaborative contextual summary interface management system 200.

Collaborative contextual summary interface data repository 215 may bestored by any suitable storage device configured to store some or all ofthe information described herein (e.g., memory 201 of the collaborativecontextual summary interface server 210 or a separate memory systemseparate from the collaborative contextual summary interface server 210,such as one or more database systems, backend data servers, networkdatabases, cloud storage devices, or the like provided by another device(e.g., online application or 3rd party provider), such as a NetworkAttached Storage (NAS) device or devices, or as a separate databaseserver or servers). Collaborative contextual summary interface datarepository 215 may comprise data received from the collaborativecontextual summary interface server 210 (e.g., via a memory 201 and/orprocessor(s) 202) and/or a client device 101A-101N, and thecorresponding storage device may thus store this data. Collaborativecontextual summary interface data repository 215 includes informationaccessed and stored by the collaborative contextual summary interfaceserver 210 to facilitate the operations of the collaborative contextualsummary interface management system 200. As such, collaborativecontextual summary interface data repository 215 may include, forexample, without limitation, presentation identifier(s), useridentifier(s), captured content identifier(s), capture typeidentifier(s), timestamp value(s), and/or the like.

The client devices 101A-101N may be implemented as any computing deviceas defined above. That is, the client devices 101A-101N may also includecircuitry, networked processors, or the like configured to perform someor all of the apparatus-based processes described herein, and mayinclude a suitable network server and/or other type of processing device(e.g., a controller or computing device of the client devices 101-101N).Electronic data received by the collaborative contextual summaryinterface server 210 from the client devices 101A-101N may be providedin various forms and via various methods. For example, the clientdevices 101A-101N may include desktop computers, laptop computers,smartphones, netbooks, tablet computers, wearables, and/or othernetworked device, that may be used for any suitable purpose in additionto presenting the collaborative contextual summary interface to a userand otherwise providing access to the collaborative contextual summaryinterface management system 200. The depictions in FIG. 1 of “N” clientdevices are merely for illustration purposes. According to someembodiments, the client devices 101A-101N may be configured to displayan interface on a display of the client device for viewing, editing,and/or otherwise interacting with at least one collaborative contextualsummary interface, which may be provided by the collaborative contextualsummary interface management system 200.

In embodiments where a client device 101A-101N is a mobile device, suchas a smartphone or tablet, the client device 101A-101N may execute an“app” to interact with the collaborative contextual summary interfacemanagement system 200. Such apps are typically designed to execute onmobile devices, such as tablets or smartphones. For example, an app maybe provided that executes on mobile device operating systems such asiOS®, Android®, or Windows®. These platforms typically provideframeworks that allow apps to communicate with one another and withparticular hardware and software components of mobile devices. Themobile operating systems named above each provide frameworks forinteracting with, for example, wired and wireless network interfaces,user contacts, and other applications. Communication with hardware andsoftware modules executing outside of the app is typically provided viaapplication programming interfaces (APIs) provided by the mobile deviceoperating system. Additionally, or alternatively, the client device101A-101N may interact with the collaborative contextual summaryinterface management system 200 via a web browser. As yet anotherexample, the client devices 101A-101N may include various hardware orfirmware designed to interface with the collaborative contextual summaryinterface management system 200. Example embodiments contemplated hereinmay have various form factors and designs but will nevertheless includeat least the components illustrated in FIG. 3 and described inconnection therewith.

Example Apparatuses for Implementing Embodiments of the PresentDisclosure

FIG. 2 shows a schematic block diagram of example circuitry, some or allof which may be included in a collaborative contextual summary interfaceserver 210. In accordance with some example embodiments, collaborativecontextual summary interface server 210 may include various means, suchas memory 201, processor 202, input/output circuitry 203, and/orcommunications circuitry 204. Moreover, in some embodiments,collaborative contextual summary interface circuitry 205 may also orinstead be included in the collaborative contextual summary interfaceserver 210. For example, where collaborative contextual summaryinterface circuitry 205 is included in collaborative contextual summaryinterface server 210, collaborative contextual summary interfacecircuitry 205 may be configured to facilitate the functionalitydiscussed herein regarding capturing content of one or more capturetypes and generating, causing storage of, updating, and/or retrievingcollaborative contextual summary interface(s). An apparatus, such ascollaborative contextual summary interface server 210, may beconfigured, using one or more of the circuitry 201, 202, 203, 204, and205, to execute the operations described above with respect to FIG. 1and below in connection with FIGS. 4-7 .

Although the use of the term “circuitry” as used herein with respect tocomponents 201-205 are described in some cases using functionallanguage, it should be understood that the particular implementationsnecessarily include the use of particular hardware configured to performthe functions associated with the respective circuitry as describedherein. It should also be understood that certain of these components201-205 may include similar or common hardware. For example, two sets ofcircuitry may both leverage use of the same processor, networkinterface, storage medium, or the like to perform their associatedfunctions, such that duplicate hardware is not required for each set ofcircuitry. It will be understood in this regard that some of thecomponents described in connection with the collaborative contextualsummary interface server 210 may be housed within this device, whileother components are housed within another of these devices, or by yetanother device not expressly illustrated in FIG. 1 .

While the term “circuitry” should be understood broadly to includehardware, in some embodiments, the term “circuitry” also includessoftware for configuring the hardware. For example, in some embodiments,“circuitry” may include processing circuitry, storage media, networkinterfaces, input/output devices, and the like. In some embodiments,other elements of the collaborative contextual summary interface server210 may provide or supplement the functionality of particular circuitry.For example, the processor 202 may provide processing functionality, thememory 201 may provide storage functionality, the communicationscircuitry 204 may provide network interface functionality, and the like.

In some embodiments, the processor 202 (and/or co-processor or any otherprocessing circuitry assisting or otherwise associated with theprocessor) may be in communication with the memory 201 via a bus forpassing information among components of, for example, collaborativecontextual summary interface server 210. The memory 201 isnon-transitory and may include, for example, one or more volatile and/ornon-volatile memories, or some combination thereof. In other words, forexample, the memory 201 may be an electronic storage device (e.g., anon-transitory computer readable storage medium). The memory 201 may beconfigured to store information, data, content, applications,instructions, or the like, for enabling an apparatus, e.g.,collaborative contextual summary interface server 210, to carry outvarious functions in accordance with example embodiments of the presentdisclosure.

Although illustrated in FIG. 2 as a single memory, memory 201 maycomprise a plurality of memory components. The plurality of memorycomponents may be embodied on a single computing device or distributedacross a plurality of computing devices. In various embodiments, memory201 may comprise, for example, a hard disk, random access memory, cachememory, flash memory, a compact disc read only memory (CD-ROM), digitalversatile disc read only memory (DVD-ROM), an optical disc, circuitryconfigured to store information, or some combination thereof. Memory 201may be configured to store information, data, applications,instructions, or the like for enabling collaborative contextual summaryinterface server 210 to carry out various functions in accordance withexample embodiments discussed herein. For example, in at least someembodiments, memory 201 is configured to buffer data for processing byprocessor 202. Additionally or alternatively, in at least someembodiments, memory 201 is configured to store program instructions forexecution by processor 202. Memory 201 may store information in the formof static and/or dynamic information. This stored information may bestored and/or used by collaborative contextual summary interface server210 during the course of performing its functionalities.

Processor 202 may be embodied in a number of different ways and may, forexample, include one or more processing devices configured to performindependently. Additionally, or alternatively, processor 202 may includeone or more processors configured in tandem via a bus to enableindependent execution of instructions, pipelining, and/ormultithreading. Processor 202 may, for example, be embodied as variousmeans including one or more microprocessors with accompanying digitalsignal processor(s), one or more processor(s) without an accompanyingdigital signal processor, one or more coprocessors, one or moremulti-core processors, one or more controllers, processing circuitry,one or more computers, various other processing elements includingintegrated circuits such as, for example, an ASIC (application specificintegrated circuit) or FPGA (field programmable gate array), or somecombination thereof. The use of the term “processing circuitry” may beunderstood to include a single core processor, a multi-core processor,multiple processors internal to the apparatus, and/or remote or “cloud”processors. Accordingly, although illustrated in FIG. 2 as a singleprocessor, in some embodiments, processor 202 comprises a plurality ofprocessors. The plurality of processors may be embodied on a singlecomputing device or may be distributed across a plurality of suchdevices collectively configured to function as collaborative contextualsummary interface server 210. The plurality of processors may be inoperative communication with each other and may be collectivelyconfigured to perform one or more functionalities of collaborativecontextual summary interface server 210 as described herein.

In an example embodiment, processor 202 is configured to executeinstructions stored in the memory 201 or otherwise accessible toprocessor 202. Alternatively, or additionally, the processor 202 may beconfigured to execute hard-coded functionality. As such, whetherconfigured by hardware or software methods, or by a combination thereof,the processor 202 may represent an entity (e.g., physically embodied incircuitry) capable of performing operations according to an embodimentof the present disclosure while configured accordingly. Alternatively,as another example, when the processor 202 is embodied as an executor ofsoftware instructions, the instructions may specifically configureprocessor 202 to perform one or more algorithms and/or operationsdescribed herein when the instructions are executed. For example, theseinstructions, when executed by processor 202, may cause collaborativecontextual summary interface server 210 to perform one or more of thefunctionalities of collaborative contextual summary interface server 210as described herein.

In some embodiments, collaborative contextual summary interface server210 further includes input/output circuitry 203 that may, in turn, be incommunication with processor 202 to provide an audible, visual,mechanical, or other output and/or, in some embodiments, to receive anindication of an input from a user, a client device 101A-101N,audio-video conferencing interface service 105, or another source. Inthat sense, input/output circuitry 203 may include means for performinganalog-to-digital and/or digital-to-analog data conversions.Input/output circuitry 203 may include support, for example, for adisplay, touchscreen, keyboard, button, click wheel, mouse, joystick, animage capturing device (e.g., a camera), motion sensor (e.g.,accelerometer and/or gyroscope), microphone, audio recorder, speaker,biometric scanner, and/or other input/output mechanisms. Input/outputcircuitry 203 may comprise a user interface and may comprise a web userinterface, a mobile application, a kiosk, or the like. The processor 202and/or user interface circuitry comprising the processor 202 may beconfigured to control one or more functions of a display or one or moreuser interface elements through computer program instructions (e.g.,software and/or firmware) stored on a memory accessible to the processor202 (e.g., memory 201, and/or the like). In some embodiments, aspects ofinput/output circuitry 203 may be reduced as compared to embodimentswhere collaborative contextual summary interface server 210 may beimplemented as an end-user machine or other type of device designed forcomplex user interactions. In some embodiments (like other componentsdiscussed herein), input/output circuitry 203 may even be eliminatedfrom collaborative contextual summary interface server 210. Input/outputcircuitry 203 may be in communication with memory 201, communicationscircuitry 204, and/or any other component(s), such as via a bus.Although more than one input/output circuitry and/or other component canbe included in collaborative contextual summary interface server 210,only one is shown in FIG. 2 to avoid overcomplicating the disclosure(e.g., like the other components discussed herein).

Communications circuitry 204, in some embodiments, includes any means,such as a device or circuitry embodied in either hardware, software,firmware or a combination of hardware, software, and/or firmware, thatis configured to receive and/or transmit data from/to a network and/orany other device, circuitry, or module in communication withcollaborative contextual summary interface server 210. In this regard,communications circuitry 204 may include, for example, a networkinterface for enabling communications with a wired or wirelesscommunication network. For example, in some embodiments, communicationscircuitry 204 is configured to receive and/or transmit any data that maybe stored by memory 201 using any protocol that may be used forcommunications between computing devices. For example, communicationscircuitry 204 may include one or more network interface cards, antennae,transmitters, receivers, buses, switches, routers, modems, andsupporting hardware and/or software, and/or firmware/software, or anyother device suitable for enabling communications via a network.Additionally or alternatively, in some embodiments, communicationscircuitry 204 includes circuitry for interacting with the antenna(s) tocause transmission of signals via the antenna(e) or to handle receipt ofsignals received via the antenna(e). These signals may be transmitted bycollaborative contextual summary interface server 210 using any of anumber of wireless personal area network (PAN) technologies, such asBluetooth® v1.0 through v3.0, Bluetooth Low Energy (BLE), infraredwireless (e.g., IrDA), ultra-wideband (UWB), induction wirelesstransmission, or the like. In addition, it should be understood thatthese signals may be transmitted using Wi-Fi, Near Field Communications(NFC), Worldwide Interoperability for Microwave Access (WiMAX) or otherproximity-based communications protocols. Communications circuitry 204may additionally or alternatively be in communication with the memory201, input/output circuitry 203 and/or any other component ofcollaborative contextual summary interface server 210, such as via abus.

In some embodiments, collaborative contextual summary interfacecircuitry 205 may also or instead be included and configured to performthe functionality discussed herein related to capturing content of oneor more capture types and generating, causing storage of, updating,and/or retrieving collaborative contextual summary interface(s). In someembodiments, collaborative contextual summary interface circuitry 205includes hardware, software, firmware, and/or a combination of suchcomponents, configured to support various aspects of such collaborativecontextual summary interface-related functionality, features, and/orservices of the collaborative contextual summary interface server 210 asdescribed herein (e.g., designed to generate a collaborative contextualsummary interface based upon at least captured content data object(s)).It should be appreciated that in some embodiments, collaborativecontextual summary interface circuitry 205 performs one or more of suchexemplary actions in combination with another set of circuitry of thecollaborative contextual summary interface server 210, such as one ormore of memory 201, processor 202, input/output circuitry 203, andcommunications circuitry 204. For example, in some embodiments,collaborative contextual summary interface circuitry 205 utilizesprocessing circuitry, such as the processor 202 and/or the like, toperform one or more of its corresponding operations. In some instances,the collaborative contextual summary interface circuitry 205 maygenerates an initial interface that is subsequently modified by capturedcontent data object(s) and/or the like. In a further example, in someembodiments, some or all of the functionality of collaborativecontextual summary interface circuitry 205 may be performed by processor202. In this regard, some or all of the example processes and algorithmsdiscussed herein can be performed by at least one processor 202 and/orcollaborative contextual summary interface circuitry 205. It should alsobe appreciated that, in some embodiments, collaborative contextualsummary interface circuitry 205 may include a separate processor,specially configured field programmable gate array (FPGA), orapplication specific interface circuit (ASIC) to perform itscorresponding functions.

Additionally or alternatively, in some embodiments, collaborativecontextual summary interface circuitry 205 utilizes memory 201 to storecollected information. For example, in some implementations,collaborative contextual summary interface circuitry 205 includeshardware, software, firmware, and/or a combination thereof, thatinteracts with collaborative contextual summary interface datarepository 215 and/or memory 201 to send, retrieve, update, and/or storedata values embodied by and/or associated with collaborative contextualsummary interface data, capture content request(s), captured contentdata object(s), user identifier(s), presentation identifier(s), capturetype identifier(s), timestamp value(s), captured content identifier(s),textual transcription data, collaborative contextual summary interfaceobject(s) and associated data that is configured for association with,for example, generating and/or updating a collaborative contextualsummary interface, and to support the operations of the collaborativecontextual summary interface circuitry 205 and the remaining circuitry.Additionally or alternatively, in some embodiments, collaborativecontextual summary interface circuitry 205 utilizes input/outputcircuitry 203 to facilitate user output (e.g., causing rendering of oneor more user interface(s) such as a collaborative contextual summaryinterface), and/or to receive user input (e.g., user clicks, user taps,keyboard interactions, user gesture, and/or the like). Additionally oralternatively still, in some embodiments, the collaborative contextualsummary interface circuitry 205 utilizes communications circuitry 204 toinitiate transmissions to another computing device, receivetransmissions from another computing device, communicate signals betweenthe various sets of circuitry as depicted, and/or the like.

Accordingly, non-transitory computer readable storage media can beconfigured to store firmware, one or more application programs, and/orother software, which include instructions and/or othercomputer-readable program code portions that can be executed to controlprocessors of the components of collaborative contextual summaryinterface server 210 to implement various operations, including theexamples shown herein. As such, a series of computer-readable programcode portions may be embodied in one or more computer program productsand can be used, with a device, collaborative contextual summaryinterface server 210, database, and/or other programmable apparatus, toproduce the machine-implemented processes discussed herein. It is alsonoted that all or some of the information discussed herein can be basedon data that is received, generated and/or maintained by one or morecomponents of the collaborative contextual summary interface server 210.In some embodiments, one or more external systems (such as a remotecloud computing and/or data storage system) may also be leveraged toprovide at least some of the functionality discussed herein.

Referring now to FIG. 3 , the client devices (e.g., client device101A-101N) or the like, may be embodied by one or more computingsystems, such as apparatus 300 shown in FIG. 3 . FIG. 3 is a schematicblock diagram showing example circuitry, some or all of which may beincluded in an example apparatus 300, configured to enable a user toaccess the collaborative contextual summary interface management system200 and/or the audio-video conferencing interface service 105 inaccordance with certain embodiments of the present disclosure. Forexample, in some embodiments, the apparatus 300 embodies a client device101A-101N and is configured to enable a user to interact with theaudio-video conferencing interface service 105 to access an activeaudio-video conference presentation that is configured for display toparticipating client devices and/or the collaborative contextual summaryinterface management system 200 to capture and/or review selectedcontent.

In accordance with some example embodiments, apparatus 300 may includevarious means, such as memory 301, processor 302, input/output circuitry303, and/or communications circuitry 304. Apparatus 300, such as aclient device 101A-101N, may be configured, using one or more of thecircuitry 301, 302, 303, and 304, to execute the operations describedabove with respect to FIG. 1 and below in connection with FIGS. 4-7 .

In some embodiments, apparatus 300 communicates with collaborativecontextual summary interface management system 200 (for example,embodied by the collaborative contextual summary interface server 210 asdepicted and described with respect to FIG. 2 ). It should beappreciated that, in some embodiments, a collaborative contextualsummary interface management system 200 communicates with any number ofapparatus(es) 300. It should be appreciated that the components 301-304may be embodied similar to that of the similarly named componentsdescribed with respect to FIG. 2 . For purposes of brevity and length ofdisclosure, duplicate description of such functionality is omitted.Nevertheless, these device elements, operating together, provide therespective apparatuses with the functionality necessary to facilitatethe communication of data (e.g., collaborative contextual summaryinterface data, capture content request(s), captured content dataobject(s), user identifier(s), presentation identifier(s), capture typeidentifier(s), timestamp value(s), captured content identifier(s),textual transcription data, collaborative contextual summary interfaceobject(s) and/or the like) for capturing content and generating acollaborative contextual summary interface. That is, the apparatus 300,in some embodiments, is configured, using one or more sets of circuitry301, 302, 303, and/or 304, to execute the operations described herein.

As described above and as will be appreciated based on this disclosure,embodiments of the present disclosure may be configured as systems,methods, apparatuses, computing devices, personal computers, servers,mobile devices, backend network devices, and the like. Accordingly,embodiments may comprise various means including entirely of hardware orany combination of software and hardware. Furthermore, embodiments maytake the form of a computer program product on at least onenon-transitory computer-readable storage medium having computer-readableprogram instructions embodied in the computer-readable storage medium(e.g., computer software stored on a hardware device). Any suitablecomputer-readable storage medium may be utilized includingnon-transitory hard disks, CD-ROMs, flash memory, optical storagedevices, or magnetic storage devices.

As will be appreciated, any such computer program instructions and/orother type of code may be loaded onto a computer, processor or otherprogrammable apparatus's circuitry to produce a machine, such that thecomputer, processor, or other programmable circuitry that execute thecode on the machine creates the means for implementing variousfunctions, including those described herein in connection with thecomponents of collaborative contextual summary interface server 210 andclient devices 101A-101N.

The computing systems described herein can include clients and servers.A client and server are generally remote from each other and typicallyinteract through a communication network. The relationship of client andserver arises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. In someembodiments, a server transmits information/data (e.g., an HTML page) toa client device (e.g., for purposes of displaying information/data toand receiving user input from a user interacting with a client device oran admin user interacting with an admin device). Information/datagenerated at the client device (e.g., as a result of the userinteraction with an admin device) can be received from the client device(e.g., client device or admin device) at the server.

Example Operations for Generating and/or Updating a CollaborativeContextual Summary Interface

In various embodiments of the present disclosure, an apparatus (e.g.,collaborative contextual summary interface server 210) is configured togenerate a collaborative contextual summary interface in associationwith an audio-video conferencing interface service. FIG. 4 illustratesan example collaborative contextual summary interface 400 in accordancewith example embodiments of the present disclosure. It should beappreciated that the information depicted in the example collaborativecontextual summary interface 400 is exemplary, and that similar and/oralternative data, parameters, data values, and/or the like may beprovided. Additionally or alternatively, in some embodiments, the layoutof the various interface elements, and/or sub-interfaces of the depictedcollaborative contextual summary interface 400 may differ withoutdeviating from scope of this disclosure. As such, the example depictedexample collaborative contextual summary interface 400, sub-interfaces,elements, and data values depicted therein are provided for descriptiveand illustrative purposes and are not to limit the scope or spirit ofthe disclosure herein.

FIG. 4 illustrates an exemplary collaborative contextual summaryinterface 400 structured in accordance with various embodiments of thepresent disclosure. In some embodiments, the collaborative contextualsummary interface 400 is configured for rendering to at least the one ofthe participating client devices 101A-101N. Additionally, oralternatively, in some embodiments, the collaborative contextual summaryinterface 400 is configured for rendering to at least the one of thenon-participating client devices 101A-101N. As illustrated, thecollaborative contextual summary interface 400 comprises one or morecaptured content interface indicators 410. Additionally, oralternatively, in some embodiments, the collaborative contextual summaryinterface 400 comprises one or more of a visual playback representationelement 420, a playback interface 430, a transcription interface 440comprising textual transcription data, one or more annotation bubbleobjects 470, a share summary interface element 450, and an exportcaptured content interface element 460. Additionally, or alternatively,in some embodiments, the collaborative contextual summary interface 400comprises one or more of a meeting information interface component(e.g., to display meeting information such as purpose, attendees, date,time, and/or the like), an emphasis interface component (e.g., todisplay one or more captured content items that have been highlighted,emphasized, or otherwise indicated as important, such as with a starindicator or icon), an object share interface component (e.g., a userinterface component that overlays the transcription interface 440 and/orthe playback interface 430 providing identification of objects beingshared, such as a link to a Confluence® page or ticket), an object statechange interface component (e.g., a user interface component thatoverlays the transcription interface 440 and/or the playback interface430 indicating state change of an object being shared, such as a Jira®ticket being resolved while it is being shared), a chat object shareinterface component (e.g., a user interface component that overlays thetranscription interface 440 and/or the playback interface 430 providingidentification of objects being shared in a chat room of the monitoredactive audio-video conferencing interface service, such as a link to aConfluence® page or ticket identified in the associated chat room), ashare interface component (e.g., including an actuator configured foruser engagement for initiating requests to share one or more interfacesor interface components with one or more other users), a breadcrumbinterface component (e.g., a user interface component revealing a user'slocation), and/or the like.

The method, apparatus (e.g., collaborative contextual summary interfaceserver 210), and computer program product of an example embodiment willnow be described in conjunction with the operations illustrated in FIGS.5A-7 . With reference to FIG. 5A, a flowchart is provided broadlyillustrating a series of operations or process blocks for collaborativecontextual summary interface generation in association with anaudio-video conferencing interface service, in accordance with someexample embodiments of the present disclosure. The operationsillustrated in FIG. 5A may, for example, be performed by, with theassistance of, and/or under the control of one or more apparatuses, suchas collaborative contextual summary interface server 210, as describedabove. In this regard, performance of the operations may invoke one ormore of memory 201, processor 202, input/output circuitry 203,communications circuitry 204, and/or collaborative contextual summaryinterface circuitry 205. Certain operations may be considered optional,as indicated by the dashed lines.

As shown in operation 505, the apparatus (e.g., collaborative contextualsummary interface server 210) includes means, such as processor 202,input/output circuitry 203, communications circuitry 204, and/or thelike, for monitoring an active audio-video conference presentation thatis configured for display to participating client devices by anaudio-video conferencing interface service. By way of example, prior toor during an active audio-video conference presentation, a user providesthe collaborative contextual summary interface server 210 with access tothe active audio-video conference presentation. For example, in someembodiments, the user provides the collaborative contextual summaryinterface server 210 with access by simply providing login credentialsand data of the audio-video conferencing interface services to thecollaborative contextual summary interface server 210. In someembodiments, the audio-video conferencing interface servicescommunicates with the collaborative contextual summary interface server210, and vice versa, through one or more application program interfaces(APIs). In some embodiments, the user provides login credentials to theaudio-video conferencing interface service, which in turn, provides thecollaborative contextual summary interface server 210 with an accesscode, which can be exchanged for one or more access tokens or otherauthentication credentials, which are then used by the collaborativecontextual summary interface server 210 to access data associated withthe active audio-video conference presentation.

In some embodiments, the active audio-video conference presentation is alive streaming presentation displayed in real time by the audio-videoconferencing interface service to each of the participating clientdevices. By way of non-limiting example, Allyson, Bethany and Cheri areusers accessing and participating in a live virtual meeting as it isdisplayed in real time. Client devices 101A-101N associated with theuser identifiers corresponding to Allyson, Bethany and Cheri are knownas participating client devices. In still other embodiments, the activeaudio-video conference presentation is a stored playback presentationthat is configured to be displayed to participating client devicesand/or non-participating client devices. By way of non-limiting example,after completion of the live streaming presentation, Allyson can use herparticipating client device to access a stored playback presentation ofthe active audio-video conference presentation. In a furthernon-limiting example, Debbie, who did not participate in the livevirtual meeting, can use her non-participating client device to accessthe stored playback presentation.

As shown by operation 510, the apparatus (e.g., collaborative contextualsummary interface server 210) includes means, such as processor 202,input/output circuitry 203, communications circuitry 204, collaborativecontextual summary interface circuitry 205 and/or the like, foridentifying a first capture content request associated with the activeaudio-video conference presentation. In some embodiments, the firstcapture content request is received from a client device 101A-101N. Byway of example, in association with an active audio-video conferencepresentation, a first user interacts with a client device 101A-101N thatis in network communication with the collaborative contextual summaryinterface server 210 to indicate an intent to capture selected contentof the monitored active audio-video conference presentation. As such, insome embodiments, this attempt to capture content by the first usergenerates and transmits a first capture content request from the clientdevice 101A-101N to the collaborative contextual summary interfaceserver 210. The first capture content request from the client device101A-101N includes, in some embodiments, various metadata relating tothe request by the first user via the client device 101A-101N. Saiddifferently, in some embodiments, the first capture content requestidentified at operation 510 comprises a first user identifier associatedwith one of the participating client devices, a first capture typeidentifier, the presentation identifier corresponding to the activeaudio-video conference presentation, and/or an initial timestamp valueassociated with the first capture content request.

In some embodiments, the user is presented with a capture contentinterface component (not shown), the capture content interface componentconfigured to display one or more selectable options corresponding tothe type of capture that the user may desire to perform with respect tothe active audio-video conference presentation. By way of non-limitingexample, during the active audio-video conference presentation, thecollaborative contextual summary interface server 210 generates,transmits, and causes rendering of a capture content interface componentto the client device, the capture content interface component comprisingthe capture type options available with respect to the correspondingactive audio-video conference presentation. In such example, Allyson ispresented with such available capture type options, such as a capturenote type, an assign action type, a capture decision type, a recordmoment type, an external service push type, capture screenshot type,object state change type, capture question type, capture answer type,capture object link type, capture sprint start, and/or the like. Inresponse to an important decision being discussed among the participantsin the active audio-video conference presentation, Allyson engages withher participating client device 101A-101N to select the optioncorresponding to the capture decision type. The client device generates(e.g., via an application operating on the client device) a capturecontent request comprising the presentation identifier of the activeaudio-video conference presentation, the capture decision typeidentifier, Allyson's user identifier, and an initial timestamp value(e.g., identifying when—such as according to UTC global standard—thecapture of media content begins). As such, depending on the capture typeselection by the user, the capture content request comprises acorresponding capture type identifier.

In some embodiments, depending on the selected capture type, aconcluding timestamp value is also included in the capture contentrequest. For example, in some embodiments, the client device 101A-101Nand/or the collaborative contextual summary interface server 210 isconfigured to request identification of and/or determine a concludingtimestamp value, the concluding timestamp value identifying when thecapture of media content ends relative to the start of a selected activeaudio-video conference presentation. For example, in some embodiments, aconcluding timestamp value is associated with completion of a userinteraction, such as no more keystrokes or receipt of the “enter”request. Subsequent interactions with the capture content will updatethe concluding timestamp value so as to encompass all interactivity withthe capture content request. Thereafter, the capture content requestwith associated metadata is transmitted to the collaborative contextualsummary interface server 210 where it is identified as a capture contentrequest associated with the active audio-video conference presentation.

Additionally or alternatively, in still further embodiments, the firstcapture content request is received from the apparatus (e.g.,collaborative contextual summary interface server 210) itself. Forexample, in some embodiments, the collaborative contextual summaryinterface server 210 is configured to automatically detect that anobject (e.g., a slide, a Jira® ticket, a Confluence® page, and/or thelike) is shared during the active audio-video conference presentation,correlate the detection with the object source (e.g., specific file),and programmatically capture a link to the associated object source toinclude in the collaborative contextual summary without requiring userinteraction to initiate the capture.

Thereafter, as shown by operation 515, the apparatus (e.g.,collaborative contextual summary interface server 210) includes means,such as processor 202, input/output circuitry 203, communicationscircuitry 204, collaborative contextual summary interface circuitry 205and/or the like, for generating a first captured content data objectbased at least in part on the first capture content request. In someembodiments, the first captured content data object comprises one ormore of the metadata associated with the first capture content requestso as to correspond to the captured content. In some embodiments, theapparatus assigns the first captured content data object a firstcaptured content identifier.

As shown by operation 520, the apparatus (e.g., collaborative contextualsummary interface server 210) includes means, such as processor 202,input/output circuitry 203, communications circuitry 204, collaborativecontextual summary interface circuitry 205 and/or the like, forcorrelating a first captured content interface indicator 410 to thefirst captured content data object. A captured content interfaceindicator 410 is a renderable indicator that can be displayed to acollaborative contextual summary interface 400, wherein the capturedcontent interface indicator 410 corresponds with the captured contentidentified by the capture content request. In some embodiments, thefirst captured content interface indicator 410 corresponds to thecapture type identifier. Continuing with the non-limiting example ofAllyson's request discussed above, the first captured content interfaceindicator associated with the captured content of Allyson's requestcorresponds to the capture decision type identifier. In someembodiments, a captured content interface indicator is selected from aplurality of captured content interface indicators 410, each capturedcontent interface indicator 410 associated with a different capture type(e.g., capture type identifier). That is, in some embodiments, capturedcontent interface indicators 410 are visually different based at leastin part on selected capture type associated with the correspondingcapture content request. For example, a captured content interfaceindicator 410 associated with an assign action type capture contentrequest may include a colored icon with a checkmark.

As shown by operation 525, the apparatus (e.g., collaborative contextualsummary interface server 210) includes means, such as processor 202,input/output circuitry 203, communications circuitry 204, collaborativecontextual summary interface circuitry 205 and/or the like, foroptionally determining a position of the first captured contentinterface indicator 410. In some embodiments, the collaborativecontextual summary interface 400 optionally comprises a visual playbackrepresentation element 420. Accordingly, in some embodiments, theapparatus determines such position relative to the visual playbackrepresentation element 420. A visual playback representation element 420is a renderable component configured to visually depict a time durationof an active audio-video conference presentation. A non-limiting exampleof a visual playback representation element 420 is a video timeline orscroll bar as depicted in FIG. 4 . In certain embodiments, one or morecaptured content interface indicators 410 are rendered to the visualplayback representation element 420. In still further embodiments, acaptured content interface indicator 410 is rendered to a position orlocation of the collaborative contextual summary interface 400 such thatit is indicative of the initial timestamp value relative to a timeduration of active-video conference presentation. For example, in someembodiments, the visual playback representation element 420 is a videotimeline or scroll bar annotated with one or more captured contentinterface indicators 410 such that the captured content is visuallyindicated in comparison to a time duration of the active audio-videoconference presentation. In some embodiments, the collaborativecontextual summary interface server 210 determines such position(s)based at least in part on the initial timestamp value(s). For example,if the initial timestamp value of the first capture content request,although captured in a global time standard such as UTC, corresponds to5 minutes and 30 seconds of elapsed time relative to the start of theselected active audio-video conference presentation and the entirety ofthe active audio-video conference presentation is 25 minutes, thecollaborative contextual summary interface server 210 determines thatthe position of the corresponding captured content interface indicator410 is approximately at ⅕ of the length of the visual playbackrepresentation element 420 (e.g., video timeline or scroll bar).

Additionally or alternatively, the collaborative contextual summaryinterface 400 optionally includes a transcription interface 440comprising textual transcription data substantially synchronized withthe active audio-video conference presentation. Accordingly, in someembodiments, the apparatus determines such position of the firstcaptured content interface indicator 410 in relation to the textualtranscription data. For example, in some embodiments, the textualtranscription data is the data output resulting from one or moretranscription operations performed with respect to one or more audioinputs of an audio visual conference presentation. As with the visualplayback representation element 420, in some embodiments, thecollaborative contextual summary interface server 210 determines theposition of the captured content interface indicator 410 based at leastin part on the initial timestamp value(s). For example, if the initialtimestamp value of the first capture content request, although capturedin a global time standard such as UTC, corresponds to 5 minutes and 30seconds of elapsed time relative to the start of the selected activeaudio-video conference presentation, the collaborative contextualsummary interface server 210 determines that the position of thecorresponding captured content interface indicator 410 in thetranscription interface 440 portion of the collaborative contextualsummary interface 400 corresponds to that timestamp value in the textualtranscription data as substantially synchronized with the activeaudio-video conference presentation. In certain embodiments, thetranscription interface 440 comprises one or more annotation bubbleobjects 470 associated with the textual transcription data and at leastone of the one or more annotation bubble objects 470 comprises the firstcaptured content interface indicator 410 as such determined position.

As shown by operation 530, the apparatus (e.g., collaborative contextualsummary interface server 210) includes means, such as processor 202,collaborative contextual summary interface circuitry 205, and/or thelike, for generating a collaborative contextual summary interface 400based at least in part on the first captured content data object. Insome embodiments, the collaborative contextual summary interface 400 isconfigured for rendering to at least the one of the participating clientdevices 101A-101N associated with the first user identifier. In stillfurther embodiments, the collaborative contextual summary interface 400comprises the first captured content interface indicator 410.

Additionally or alternatively, as shown by operation 535, the apparatus(e.g., collaborative contextual summary interface server 210) includesmeans, such as processor 202, input/output circuitry 203, communicationscircuitry 204, collaborative contextual summary interface circuitry 205and/or the like, for optionally storing the collaborative contextualsummary interface 400 in a collaboration repository (e.g., collaborativecontextual summary interface data repository 215) in association withthe presentation identifier.

Thereafter, as shown by operation 540, the apparatus (e.g.,collaborative contextual summary interface server 210) includes means,such as processor 202, input/output circuitry 203, communicationscircuitry 204, collaborative contextual summary interface circuitry 205and/or the like, for optionally causing rendering of the collaborativecontextual summary interface 400 to a client device (e.g., aparticipating client device associated with the first user identifier).For example, in some embodiments, the collaborative contextual summaryinterface circuitry 205 transmits an instruction to the client device101A-101N to render the collaborative contextual summary interface 400for viewing by at least the requesting user (e.g., Allyson).Additionally, in still further embodiments, the collaborative contextualsummary interface circuitry 205 transmits instructions to one or moreclient devices 101A-101N other than the first user (e.g., otherparticipating client devices and/or non-participating client devices) torender the collaborative contextual summary interface 400 for viewing byone or more users other than the requesting user, such that thecollaborative contextual summary interface 400 comprising the firstcaptured content interface indicator 410 is then shared among the otherclient devices 101A-101N via the collaborative contextual summaryinterface server 210. For example, the collaborative contextual summaryinterface 400 is rendered to client devices 101A-101N during a livestreaming presentation (e.g., participating client devices) and/or astored playback presentation (e.g., participating and/ornon-participating client devices) of the active audio-video conferencepresentation such that collaborative contextual summary interface 400 isviewable by the first user (e.g., the requesting user, Allyson) andanother user other than the first user (e.g., a second user such asBethany).

In some embodiments, in causing rendering of the collaborativecontextual summary interface 400 to a client device, the first capturedcontent interface indicator 410 is displayed to the collaborativecontextual summary interface 400 in the determined position (e.g.,according to optional operation 525) relative to the visual playbackrepresentation element 420. As described hereafter with reference toFIG. 6 , during viewing of an active audio-video conferencepresentation, in some embodiments, the collaborative contextual summaryinterface 400 is iteratively updated based upon one or more capturedcontent data object(s) corresponding to captured content requestsadditionally identified by the apparatus (e.g., collaborative contextualsummary interface server 210). For example, in some embodiments, thecollaborative contextual summary interface 400 includes one or morecaptured content interface indicators 410 corresponding to a variety ofidentified capture content requests generated by one or moreparticipating and/or non-participating client devices.

In some embodiments, the collaborative contextual summary interface 400optionally comprises a share summary interface element 450. The sharesummary interface element 450 includes an actuator configured for userengagement for initiating requests to share the collaborative contextualsummary interface 400 with one or more other users. Accordingly,additionally or alternatively, in certain embodiments, the apparatus(e.g., collaborative contextual summary interface server 210) includesmeans, such as processor 202, input/output circuitry 203, communicationscircuitry 204, collaborative contextual summary interface circuitry 205,and/or the like, for, upon detection of user engagement with the sharesummary interface element 450, optionally generating a collaborativecontextual summary interface object that is configured to cause a clientdevice 101A-101N to render the collaborative contextual summaryinterface 400. By way of non-limiting example, upon detection of userengagement with the share summary interface element 450, thecollaborative contextual summary interface server 210 generates an MP4,URL, or similar data object corresponding to the captured content of thecollaborative contextual summary interface 400 and outputs the dataobject (e.g., MP4) to a client device 101A-101N other than theparticipating client device of the requesting user. For example, userengagement with the share summary interface element 450 may trigger arequest for identification of one or more intended recipients (e.g.,participating and/or non-participating) of the collaborative contextualsummary interface 400.

Thereafter, in some embodiments, the apparatus (e.g., collaborativecontextual summary interface server 210) includes means, such asprocessor 202, input/output circuitry 203, communications circuitry 204,collaborative contextual summary interface circuitry 205, and/or thelike, for, upon detection of user engagement with the share summaryinterface element 450, optionally outputting the collaborativecontextual summary interface object (e.g., MP4) to one or more clientdevices 101A-101N. In some embodiments, the apparatus (e.g.,collaborative contextual summary interface server 210) includes means,such as processor 202, input/output circuitry 203, communicationscircuitry 204, collaborative contextual summary interface circuitry 205,and/or the like, for, upon detection of user engagement with thecollaborative contextual summary interface object, optionally causingrendering of the collaborative contextual summary interface 400 to thecorresponding client devices. In some embodiments, one or more intendedrecipients are associated with participating client devices.Additionally or alternatively, one or more intended recipients areassociated with non-participating client devices.

Additionally or alternatively, in still further embodiments, thecollaborative contextual summary interface 400 optionally comprises anexport captured content interface element 460. In some embodiments, forexample, an export captured content interface element 460 includes oneor more actuators configured for user engagement for initiating requeststo export collaborative contextual summary interface data (e.g., dataassociated with an capture content identifier and/or data object) to oneor more other internal or external services.

FIG. 5B is a signal diagram of an example data flow represented by theoperations depicted in FIG. 5A. That is, FIG. 5B illustrates an examplesignal diagram illustrating data flow interactions between acollaborative contextual summary interface server, a client device, anda repository, when generating a collaborative contextual summaryinterface in accordance with one embodiment. FIG. 5B is described asbeing performed by a collaborative contextual summary interface server210, a collaborative contextual summary interface data repository 215,and a client device 101A. These may be similar to those previouslydiscussed with regards to FIG. 1 .

Turning now to FIG. 6 , a flowchart broadly illustrates another seriesof operations or process blocks for updating a collaborative contextualsummary interface, in accordance with some example embodiments of thepresent disclosure. The example operations of FIG. 6 are illustratedfrom the perspective of a collaborative contextual summary interfacemanagement system 200. The operations illustrated in FIG. 6 may, forexample, be performed by, with the assistance of, and/or under thecontrol of one or more apparatuses, such as collaborative contextualsummary interface server 210, as described above. In this regard,performance of the operations may invoke one or more of memory 201,processor 202, input/output circuitry 203, communications circuitry 204,and/or collaborative contextual summary interface circuitry 205.

In the embodiment illustrated in FIG. 6 , as shown in operation 605, theapparatus (e.g., collaborative contextual summary interface server 210)includes means, such as input/output circuitry 203, communicationscircuitry 204, collaborative contextual summary interface circuitry 205and/or the like, for identifying a second capture content requestassociated with the active audio-video conference presentation. In someembodiments, the second capture content request is received from aclient device 101A-101N associated with the first user identifier. Byway of example, in association with the active audio-video conferencepresentation as discussed with respect to FIG. 5A, the first user againinteracts with a client device 101A-101N that is in networkcommunication with the collaborative contextual summary interface server210 to indicate an intent to capture additionally selected content ofthe monitored active audio-video conference presentation. Similar to thediscussion of operation 510, in some embodiments, this attempt tocapture additional content by the first user generates and transmits asecond capture content request from the client device 101A-101N to thecollaborative contextual summary interface server 210. The secondcapture content request from the client device 101A-101N includes, insome embodiments, a second capture type identifier, the presentationidentifier corresponding to the active audio-video conferencepresentation, and/or an initial timestamp value associated with thesecond capture content request.

In an alternative embodiment, the second capture content request isreceived from a client device 101A-101N associated with a second user.By way of example, in association with the active audio-video conferencepresentation as discussed with respect to FIG. 5A, a second userinteracts with a client device 101A-101N that is in networkcommunication with the collaborative contextual summary interface server210 to indicate an intent to capture selected content of the monitoredactive audio-video conference presentation. Similar to the discussion ofoperation 510, in some embodiments, this attempt to capture content bythe second user generates and transmits a second capture content requestfrom the client device 101A-101N to the collaborative contextual summaryinterface server 210. The second capture content request from the clientdevice 101A-101N includes, in some embodiments, a second user identifierassociated with second user, a second capture type identifier, thepresentation identifier corresponding to the active audio-videoconference presentation, and/or an initial timestamp value associatedwith the second capture content request.

Thereafter, as shown by operation 610, the apparatus (e.g.,collaborative contextual summary interface server 210) includes means,such as processor 202, input/output circuitry 203, communicationscircuitry 204, collaborative contextual summary interface circuitry 205and/or the like, for generating a second captured content data objectbased at least in part on the second capture content request. In someembodiments, the second captured content data object comprises one ormore of the metadata associated with the second capture content requestso as to correspond to the captured content. In some embodiments, theapparatus assigns the second captured content data object a secondcaptured content identifier 410.

As shown by operation 615, the apparatus (e.g., collaborative contextualsummary interface server 210) includes means, such as processor 202,input/output circuitry 203, communications circuitry 204, collaborativecontextual summary interface circuitry 205 and/or the like, forcorrelating a second captured content interface indicator 410 to thesecond captured content data object, wherein the captured contentinterface indicator 410 corresponds with the captured content identifiedby the capture content request. In some embodiments, the second capturedcontent interface indicator 410 corresponds to the second capture typeidentifier.

As shown by operation 620, the apparatus (e.g., collaborative contextualsummary interface server 210) includes means, such as processor 202,collaborative contextual summary interface circuitry 205, and/or thelike, for updating the collaborative contextual summary interface (e.g.,as previously generated in operation 530 of FIG. 5A) based at least inpart on the second captured content data object such that thecollaborative contextual summary interface 400 comprises the firstcaptured content interface indicator 410 and the second captured contentinterface indicator 410. In the exemplary instance where the secondcapture content request is generated by the same user as the firstcapture content request (e.g., first user), the collaborative contextualsummary interface 400 is configured for rendering to at least the one ofthe participating client devices associated with the first useridentifier. In the exemplary instance where the second capture contentrequest is generated by the second user, the collaborative contextualsummary interface 400 is configured for rendering to at least the one ofthe participating client devices associated with the first useridentifier and at least the one of the participating client devicesassociated with the second user identifier.

Additionally, or alternatively, in some embodiments wherein the activeaudio-video conference presentation is a live streaming presentationdisplayed in real time by the audio-video conferencing interface serviceto each of the participating client devices, updating the collaborativecontextual summary interface 400 based at least in part on the secondcaptured content data object comprises iteratively updating thecollaborative contextual summary interface 400 in real time. Similarly,in some embodiments wherein the active audio-video conferencepresentation is a stored playback presentation, iteratively updating thecollaborative contextual summary interface 400 based at least in part onthe second captured content data object comprises updating thecollaborative contextual summary interface 400 in real time.

Turning now to FIG. 7 , a flowchart broadly illustrates another seriesof operations or process blocks for updating a collaborative contextualsummary interface, in accordance with some example embodiments of thepresent disclosure. The example operations of FIG. 7 are illustratedfrom the perspective of a collaborative contextual summary interfacemanagement system 200. The operations illustrated in FIG. 7 may, forexample, be performed by, with the assistance of, and/or under thecontrol of one or more apparatuses, such as collaborative contextualsummary interface server 210, as described above. In this regard,performance of the operations may invoke one or more of memory 201,processor 202, input/output circuitry 203, communications circuitry 204,and/or collaborative contextual summary interface circuitry 205.

In the embodiment illustrated in FIG. 7 , as shown in operation 705, theapparatus (e.g., collaborative contextual summary interface server 210)includes means, such as input/output circuitry 203, communicationscircuitry 204, collaborative contextual summary interface circuitry 205and/or the like, for detecting user engagement with the first capturedcontent interface indicator 410. For example, in some embodiments, theclient device 101A-101N is configured to generate an engagement event inresponse to user engagement with the first captured content interfaceindicator 410 and thereafter transmit such engagement event to thecollaborative contextual summary interface server 210.

As shown in operation 710, the apparatus (e.g., collaborative contextualsummary interface server 210) includes means, such as input/outputcircuitry 203, communications circuitry 204, collaborative contextualsummary interface circuitry 205 and/or the like, for updating thecollaborative contextual summary interface 400 to display a storedplayback presentation of at least a portion of the active audio-videoconference presentation, wherein the stored playback presentationcommences with rendering of media content of the active audio-videoconference presentation corresponding to the initial timestamp valueassociated with the first captured content interface indicator 410. Asdiscussed herein, the first captured content interface indicator 410 canbe rendered to one or more of a visual playback representation element420 and an annotation bubble object 470. In some embodiments, forexample, in certain instances wherein the first captured contentinterface indicator 410 is associated with a visual playbackrepresentation element 420 and/or an annotation bubble object 470 (e.g.,in the transcription interface 440), the collaborative contextualsummary interface server 210 causes the stored playback presentation tocontinue presenting until complete and/or stopped by the user.Additionally or alternatively, in some embodiments, for example, certaininstances wherein the user engages a first captured content interfaceindicator 410 associated with an annotation bubble object 470, thecollaborative contextual summary interface server 210 concludes withrendering of media content of the active audio-video conferencepresentation corresponding to a concluding timestamp value.

FIGS. 5A, 5B, 6, and 7 thus illustrate flowcharts and signal diagramsdescribing the operation of apparatuses, methods, systems, and computerprogram products according to example embodiments contemplated herein.It will be understood that each flowchart block, and combinations offlowchart blocks, may be implemented by various means, such as hardware,firmware, processor, circuitry, and/or other devices associated withexecution of software including one or more computer programinstructions. For example, one or more of the operations described abovemay be implemented by an apparatus executing computer programinstructions. In this regard, the computer program instructions may bestored by a memory 201 of the collaborative contextual summary interfaceserver 210 and executed by a processor 202 of the collaborativecontextual summary interface server 210. As will be appreciated, anysuch computer program instructions may be loaded onto a computer orother programmable apparatus (e.g., hardware) to produce a machine, suchthat the resulting computer or other programmable apparatus implementsvarious functions, including those functions specified in the flowchartblocks. These computer program instructions may also be stored in acomputer-readable memory that may direct a computer or otherprogrammable apparatus to function in a particular manner, such that theinstructions stored in the computer-readable memory produce an articleof manufacture, the execution of which implements the functionsspecified in the flowchart blocks. The computer program instructions mayalso be loaded onto a computer or other programmable apparatus to causea series of operations to be performed on the computer or otherprogrammable apparatus to produce a computer-implemented process suchthat the instructions executed on the computer or other programmableapparatus provide operations for implementing the functions specified inthe flowchart blocks.

The flowchart blocks support combinations of means for performing thespecified functions and combinations of operations for performing thespecified functions. It will be understood that one or more blocks ofthe flowcharts, and combinations of blocks in the flowcharts, can beimplemented by special purpose hardware-based computer systems whichperform the specified functions, or combinations of special purposehardware with computer instructions.

Thus, particular embodiments of the subject matter have been described.While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinventions or of what may be claimed, but rather as description offeatures specific to particular embodiments of particular inventions.Other embodiments are within the scope of the following claims. Certainfeatures that are described herein in the context of separateembodiments can also be implemented in combination in a singleembodiment. Conversely, various features that are described in thecontext of a single embodiment can also be implemented in multipleembodiments separately or in any suitable sub-combination. Moreover,although features may be described above as acting in certaincombinations and even initially claimed as such, one or more featuresfrom a claimed combination can in some cases be excised from thecombination, and the claimed combination may be directed to asub-combination or variation of a sub-combination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults, unless described otherwise. In certain circumstances,multitasking and parallel processing may be advantageous. Moreover, theseparation of various system components in the embodiments describedabove should not be understood as requiring such separation in allembodiments, and it should be understood that the described programcomponents and systems can generally be integrated together in a singlesoftware product or packaged into multiple software products. Anyoperational step shown in broken lines in one or more flow diagramsillustrated herein are optional for purposes of the depicted embodiment.

In some cases, the actions recited in the claims can be performed in adifferent order and still achieve desirable results. In addition, theprocesses depicted in the accompanying figures do not necessarilyrequire the particular order shown, or sequential order, to achievedesirable results, unless described otherwise. In certainimplementations, multitasking and parallel processing may beadvantageous.

CONCLUSION

Many modifications and other embodiments of the present disclosure setforth herein will come to mind to one skilled in the art to which thisdisclosure pertains having the benefit of the teachings presented in theforegoing descriptions and the associated drawings. Therefore, it is tobe understood that the disclosure is not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Moreover, although the foregoing descriptions and the associateddrawings describe example embodiments in the context of certain examplecombinations of elements and/or functions, it should be appreciated thatdifferent combinations of elements and/or functions may be provided byalternative embodiments without departing from the scope of the appendedclaims. In this regard, for example, different combinations of elementsand/or functions than those explicitly described above are alsocontemplated as may be set forth in some of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation.

What is claimed is:
 1. An apparatus configured to generate acollaborative contextual summary interface in association with anaudio-video conferencing interface service, the apparatus comprising atleast one processor and at least one memory, the at least one memoryhaving computer-coded instructions therein, wherein the computer-codedinstructions are configured to, in execution with the at least oneprocessor, cause the apparatus to: monitor an active audio-videoconference presentation that is configured for display to participatingclient devices by the audio-video conferencing interface service;identify a capture content request associated with the activeaudio-video conference presentation, wherein the capture content requestcomprises an object shared by at least one of the participating clientdevices during the active audio-video conference presentation; correlatethe shared object to an external service object source; generate acaptured content data object based at least in part on the capturecontent request, wherein the captured content data object comprises aselectable link to the external service object source; and generate acollaborative contextual summary interface based at least in part on thecaptured content data object, wherein the collaborative contextualsummary interface comprises an object share interface componentcomprising the selectable link to the external service object source,and wherein the collaborative contextual summary interface is configuredfor rendering to at least the one of the participating client devices.2. The apparatus of claim 1, wherein the collaborative contextualsummary interface further comprises a transcription interface, thetranscription interface comprising textual transcription datasubstantially synchronized with the active audio-video conferencepresentation.
 3. The apparatus of claim 2, wherein the object shareinterface component is a user interface component overlaying thetranscription interface.
 4. The apparatus of claim 3, wherein the objectshare interface component is an annotation bubble object comprising theselectable link to the external service object source and a capturedcontent interface indicator corresponding to the captured content dataobject.
 5. The apparatus of claim 4, wherein the computer-codedinstructions are further configured to, in execution with the at leastone processor, cause the apparatus to: cause rendering of thecollaborative contextual summary interface to the at least one of theparticipating client devices in real time.
 6. The apparatus of claim 1,wherein the collaborative contextual summary interface comprises aplayback interface and a visual playback representation element, thevisual playback representation element representing a time duration ofthe active audio-video conference presentation.
 7. The apparatus ofclaim 6, wherein the computer-coded instructions are further configuredto, in execution with the at least one processor, cause the apparatusto: correlate a captured content interface indicator to the capturedcontent data object; determine a position of the captured contentinterface indicator relative to the visual playback representationelement; and causing rendering of the collaborative contextual summaryinterface to the at least one of the participating client devices, suchthat the captured content interface indicator is displayed to thecollaborative contextual summary interface in the determined positionrelative to the visual playback representation element.
 8. The apparatusof claim 7, wherein the capture content request is associated with aninitial timestamp value and wherein the determined position is based atleast in part on the initial timestamp value relative to the timeduration of the active audio-video conference presentation.
 9. Theapparatus of claim 1, wherein the collaborative contextual summaryinterface comprises a plurality of captured content interfaceindicators, each captured content interface indicator associated with acorresponding captured content data object from the active audio-videoconference presentation.
 10. The apparatus of claim 9, wherein thecollaborative contextual summary interface further comprises an exportcaptured content interface element, wherein the export captured contentinterface element is configured for user engagement for initiatingrequests to export collaborative contextual summary interface data toone or more internal or external services.
 11. The apparatus of claim10, wherein the computer-coded instructions are further configured to,in execution with the at least one processor, cause the apparatus to:identify an export captured content request associated with the capturedcontent data object from the active audio-video conference presentation;and export the captured content data object to the one or more internalor external services.
 12. The apparatus of claim 1, wherein the activeaudio-video conference presentation is a live streaming presentationdisplayed in real time by the audio-video conferencing interface serviceto each of the participating client devices.
 13. A computer-implementedmethod, the method comprising: monitoring an active audio-videoconference presentation that is configured for display to participatingclient devices by an audio-video conferencing interface service;identifying a capture content request associated with the activeaudio-video conference presentation, wherein the capture content requestcomprises an object shared by at least one of the participating clientdevices during the active audio-video conference presentation;correlating the shared object to an external service object source;generating a captured content data object based at least in part on thecapture content request, wherein the captured content data objectcomprises a selectable link to the external service object source; andgenerating a collaborative contextual summary interface based at leastin part on the captured content data object, wherein the collaborativecontextual summary interface comprises an object share interfacecomponent comprising the selectable link to the external service objectsource, and wherein the collaborative contextual summary interface isconfigured for rendering to at least the one of the participating clientdevices.
 14. The computer-implemented method of claim 13, wherein thecollaborative contextual summary interface further comprises atranscription interface, the transcription interface comprising textualtranscription data substantially synchronized with the activeaudio-video conference presentation.
 15. The computer-implemented methodof claim 14, wherein the object share interface component is a userinterface component overlaying the transcription interface.
 16. Thecomputer-implemented method of claim 15, wherein the object shareinterface component is an annotation bubble object comprising theselectable link to the external service object source and a capturedcontent interface indicator corresponding to the captured content dataobject.
 17. The computer-implemented method of claim 13, wherein thecollaborative contextual summary interface comprises a playbackinterface and a visual playback representation element, the visualplayback representation element representing a time duration of theactive audio-video conference presentation.
 18. The computer-implementedmethod of claim 17, the method further comprising: correlating acaptured content interface indicator to the captured content dataobject; determining a position of the captured content interfaceindicator relative to the visual playback representation element; andrendering the collaborative contextual summary interface to the at leastone of the participating client devices, such that the captured contentinterface indicator is displayed to the collaborative contextual summaryinterface in the determined position relative to the visual playbackrepresentation element.
 19. The computer-implemented method of claim 18,wherein the capture content request is associated with an initialtimestamp value and wherein the determined position is based at least inpart on the initial timestamp value relative to the time duration of theactive audio-video conference presentation.
 20. The computer-implementedmethod of claim 13, wherein the collaborative contextual summaryinterface comprises a plurality of captured content interfaceindicators, each captured content interface indicator associated with acorresponding captured content data object from the active audio-videoconference presentation.
 21. The computer-implemented method of claim20, wherein the collaborative contextual summary interface furthercomprises an export captured content interface element, wherein theexport captured content interface element is configured for userengagement for initiating requests to export collaborative contextualsummary interface data to one or more internal or external services. 22.The computer-implemented method of claim 21, the method furthercomprising: identifying an export captured content request associatedwith the captured content data object from the active audio-videoconference presentation; and exporting the captured content data objectto the one or more internal or external services.
 23. Thecomputer-implemented method of claim 13, wherein the active audio-videoconference presentation is a live streaming presentation displayed inreal time by the audio-video conferencing interface service to each ofthe participating client devices.
 24. The computer-implemented method ofclaim 23, the method further comprising: rendering the collaborativecontextual summary interface to the at least one of the participatingclient devices in real time.